The title pretty much says it all. When executing an action on a subtree in a dired buffer (such as moving or deleting files), these files are still displayed because the buffer is not refreshed. This does not happen on non-subtreed dired buffers. I tried to investigate things a little and I would guess this would have something to do with the dired-after-readin-hook not activating.