Best approach for managing HSL connections

Ahh yes, I have been seeing some scant references to HSL doing it's own management, but barely enough to actually confirm what's going on under the covers. If it pools effectively, then that naturally removes any scaling issues, and you happily throw opens around when you feel like it? All sounds good to me then. So if we're requesting a handle when is that handle freed? on the close of the connection? Or would that only be if if was opened in the equivalently scoped event? Like.... if we open on HTTP_REQUEST, would the back ground events of HTTP_RESPONSE close it? I imagine that it's more relevant that this doesn't actually matter.

Currently we're only logging small volumes to a syslog-ng service, but hopefully this will be laying the groundwork to heavily expand logging to a Splunk farm so just looking to do the groundwork mostly.

Thanks!