Some CometHandler can always invoke, during the same transaction, the
addCometHandler, and the spawn a Thread and invoke the resumeCometHandler. In
that situation, the Response object might be invoked twice (once when Grizzly
resume it, one when the CometHandler does the same things), corrupting the
response (as the response get the last chunked bytes twice). Fix is easy.