We don't have that particular setting. I've never really seen the reason for it. If the client is sending regular request, then closing the connection after N requests will just make it open a new connection, which is more work for everybody? Maybe tomcat offers it as some kind of memory leak clearance, but jetty doesn't have any such leaks, so we never have seen the need.
Ah I see your reason is that you want better load balancing. Well rather than have some code counting requests and connections, you can probably just have a filter that randomly adds the Connection:close header to the response and that will give you pretty much the same effect of helping level your load balancer.
You can also look at our lowResourcesMonitor and DoSFilter for other approaches that may help.
cheers
