As a result of calling exitScheduler(), enter into a
'shutting-down' state, so that the subsequent (sequential)
execution of finalisers won't get stuck inside the
Scheduler waiting for more work.

Cleanest way I could think of solving this problem on a
Friday afternoon.