Nice article, thanks for sharing.
IMHO this is a very important modification in the behaviour of the ThreadPool.
Anyway I wouldn't consider it "breaking", since an application based on multi-threading processing should be much more fault-tolerant about resources management, so if your application stopped working, maybe you could consider a more robust and flexible architecture.
That's just my 2 cents :)

And what will be the next overlooked feature ? The "for" loop :S ?