This means that the Selector will be alive for a _while_ after postStop finishes. If the old behavior was intentional, it should've been documented and hopefully tested. I can switch back and use the same stunt as with `wakeup` for `stop` but I'd rather keep it as is now.
Thoughts?