Currently the users have no chance to turn on the KEEP-ALIVE option for the sockets created by jetty in configuration files. But it is really important, especially for continuation:
For example, a use made a long polling, and waiting on a continuation. Then user plugged the network cable out of the computer, shutdown the computer, and went home. In the jetty side, we never know the user has left without a KEEP-ALIVE socket connection, and continuation is be in jetty forever until jetty restart.
A similar issue is: http://jira.codehaus.org/browse/JETTY-593 . But in 593, the process of web browser will send a FIN to jetty server. But in this case, nothing will be send to notify the jetty server.