ICAP connections under heavy loads

Hi! My setup is Squid 3.2.1 + C-ICAP Antivirus.

I noticed that in simulated production setup (e.g. 1200 http requests
per sec) there are dozens connections established from squid to c-icap
server, and even after the last client request timeouts, these
connections are still opened/opening.

tcp 0 0 127.0.0.1:1344 127.0.0.1:51352
ESTABLISHED
tcp 722 0 127.0.0.1:1344 127.0.0.1:51500
ESTABLISHED
tcp 0 0 127.0.0.1:51374 127.0.0.1:1344
ESTABLISHED
tcp 0 0 127.0.0.1:1344 127.0.0.1:51404
ESTABLISHED
tcp 0 0 127.0.0.1:51370 127.0.0.1:1344
ESTABLISHED
tcp 0 0 127.0.0.1:51375 127.0.0.1:1344
ESTABLISHED
tcp 722 0 127.0.0.1:1344 127.0.0.1:51454
ESTABLISHED
tcp 0 0 127.0.0.1:1344 127.0.0.1:51373
ESTABLISHED
tcp 722 0 127.0.0.1:1344 127.0.0.1:51427
ESTABLISHED
tcp 0 1 127.0.0.1:51677 127.0.0.1:1344
SYN_SENT
tcp 0 0 127.0.0.1:51211 127.0.0.1:1344
TIME_WAIT
tcp 0 0 127.0.0.1:51420 127.0.0.1:1344
ESTABLISHED
tcp 0 0 127.0.0.1:1344 127.0.0.1:51318
ESTABLISHED
tcp 0 0 127.0.0.1:51290 127.0.0.1:1344
ESTABLISHED

Is this the intended behavior?

Also there are a lot of "BUG: Orphaned connection" messages in my
cache.log under those conditions. I found out that they are caused by
Xaction destruction after client request timeout, getting
noteInitiatorAborted() before connection is established in the
corresponding ConnOpener job. I temporarily fixed that by notifying
ConnOpener (if any) in the Xaction::swanSong().

-- 
Best wishes,
Alexander Komyagin