Prevent Blaze.remove from doing extra detaches

(The test doesn’t really cover the case we encountered in iron-layout.)

It’s normal to end up calling Blaze.remove on an already-destroyed View, or a View that is not attached directly the DOM but has a parentRange (it’s just that it takes a situation like iron-layout to actually have a pointer to such a View in your code).