It has been observed  (SERVER-60387) that removeShard() may prevent range deletion tasks from being executed when the removed node is the recipient of a chunk being moved and it is being shut down while the migration is completing. This scenario should be avoided.

Evaluate whether it's feasible to drain range deletions and delete all orphans (simply issuing a local dropCollection) when running removeShard.