We've observed one failure to close all open cursors. I suspect it's because some internal operations are opening cursors and interfering with the test, so logging which operations remain active with open cursors at the end of the test will hopefully let us confirm or deny that theory.

I was unable to reproduce the issue so I'd like to commit the improved diagnostic message and wait for it to happen again.