Just FTR: With this change you are removing this QTP
https://github.com/sonatype/sisu-jetty8/commit/0cf9572896d4f0cf77bbaa57c41359db86cf9586

Some context about it here:
http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02350.html

And (unrelated) issue describing Greg's stance wrt OOM here:
http://jira.codehaus.org/browse/JETTY-1194

Short summary: Jetty is silent about thread death, it does not inform you in any way that a thread was removed from a pool. While this problem with P2 was a special case (one single point acquired huge amounts of heap, that is immediately put out of scope, the P2 repo metadata DOM). But the point is, that the fact that QTP thread doing working on P2 related request was not logged anywhere, there was not signs at all, simply that one single request failed, and Nexus happily continued running, everything was seemingly working just fine. 

While I do share Greg's concerns about OOM, the problem is that there is no feedback at all about OOM happened. And due to the nature of it, Nexus just continued happily working.