Just occured to me if Im leaking REQUEST it would be nice to see exactly
which requests im leaking. But is that really covered by the -M logger, if a
request fails to be closed in there does that really translate to a leaked
request? I had a look in the code and it wasn't obvious to me
It's not covered by the data output into the -M log. Objects can leak
without requests hanging or taking a long time. But you might be able to
turn on profiling (set the PROFILE_PUBLISHER env var to a filename and
restart Zope) on a *test* box (do not do it in production, it drastically
