break zoomark's dependency on pool_threadlocal, zoomark_orms dependency on engine-bound session
investigate why zoomark requires pool_threadlocal. it seems to be using autocommit so there shouldn't be issues turning it off but I was getting data errors, etc. I hardly looked at it at all so might be something simple.
zoomark_orm also seems to require that the session is bound to the engine directly instead of pulling it from metadata. Might be something simple as well.