IIS WebServices (XML/SOAP)

I am running 4x IIS6.0 Webservices servers and have been monitoring
connections on the f5 load balancer and perfmon'ing the sites. 2 used
HTTP Keep Alives and had a steady number of connections...the other 2
had keep disabled and 0 connections, although IIS logs reported the
amount of connections/requests being handled.

Now I realise that without keepalives connections are cleaned up, but
my question is whether to use Keep Alives with WebServices
anyway......they are pretty much asyncronous calls and non session
based.......posts and results, so probably no need to keep alive the
connection right??? As Keep-alives are more use with user type sites.

If you have any experience with webservices and this setting, I'd like
to know your thoughts. Is there a performance benefit of using HTTP
Keep Alives? Is there any point??