This affects latest NX2 it seems. NX2 claims it will keep alive the connection (default with HTTP/1.1) and even ensures it with a header if client is HTTP/1.0 (as with that protocol level extra header Connection: keep-alive is needed), but then immediately drops connection on response is sent. This leaves no chance for connection pooling clients (like NX2/NX3, unlike Wagons) to properly handle connections, as connections returned to pool and believed to be alive will be actually immediately closed.
OOTB Jetty 8 does not do this, this has to be something in NX2.
Either fix the
a) connection to remain alive if said so, or
b) as simpler fix just add "Connection: close" header when client is HTTP/1.1 and prevent addition of (done by Jetty) "Connection: keep-alive" header when client is HTTP/1.0
Marked as affects 2.11.3, but it might affect other 2.x versions too.