doc patch to fix what looks to be a circular reference

I've not checked it to see if it is a memory leak, but it looks like one, and we had a bad leak in our code based on this until it was changed.