JAX-WS Client Raises Jetty EofException

I use the built-in Jetty server to provide web services (using Jetty-JAXWS2-SPI to allow Jetty to handle requests), and I see the following errors when the connection terminates from my JAX-WS test client (generated wsimport):

11:32:54.544 [pool-1-thread-5] DEBUG com.mycompany.SomeClass - EOF
org.eclipse.jetty.io.EofException: null
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:321) ~[jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307]
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214) ~[jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307]
        at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411) ~[jetty-server-7.3.1.v20110307.jar:7.3.1.v20110307]
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:526) ~[jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307]
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:41) [jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_24]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_24]
        at java.lang.Thread.run(Thread.java:662) [na:1.6.0_24]

Despite the fact that these are not important errors (recorded at the DEBUG level), and I see them only from my test client, and not from soapUI or the "real" (.NET client), I would not see them at all.

I think the problem is with the socket behavior in the JAX-WS client? Is there a way to influence socket behavior to avoid this problem?

Additional Information:

• Others reported this issue on the Jetty mailing list, also when providing web services using the Jetty-JAXWS2-SPI.
• JDK 1.6.0_24 JAX-WS.
• Jetty 7.3.1-20110307