In developing a large new feature for our web app, we ran into this problem as well. We use an XHR request from the JS client to get user favorites from the Tomcat server hosted on Amazon Linux. The initial connection works fine as expected. However, the second identical request fails with "Failed to load resource: the network connection was lost" in the client JS console. I suspect Safari recognizes the second request as a mistaken duplicate of the first.
The current workaround we are using for Tomcat is to effectively disable KeepAlive support. Unfortunately, this affects all connections, not just for Safari on desktop and/or mobile. This solution for Tomcat is to set a parameter on the Connector for HTTPS in ${CATALINA_HOME}/conf/server.xml...
maxKeepAliveRequests="1"
There might be other solutions to limit the damage to only Safari connections. If I discover them, I'll come back and update this post. The better band aid would be to cache results in our app and avoid the problem altogether.