This was originally reported under issue #70.

My intuition as to what was the underlying issue was a bit off the mark.

Rather I believe that in the event that connectEndpoint_p fails to connect to a worker:

At this point, for this scheduler instance, after doReject, $workers[workerId].promise -> rejection, however if the worker never fulfills
its exit promise (it's stuck churning away for whatever reason), the scheduler instance remains hanging around
with ($workers[Object.keys(this.$workers)[0]].promise) still pointing at that rejection.
This would handicap all future requests pointing at this appSpec, in the simple-scheduler model.

Let me know if this doesn't make sense.

Thanks