Comment 2 for bug 934575

Thanks! My initial instinct was to not store connection_pool in the context but to just pass it as an arg to msg_reply.... however... that wouldn't work for the case where you can do a context.reply() in a manager. Now... we don't use that behavior currently, though... and I wonder how useful it is. If we can ditch the context.reply() support, the fix is rather easy.

Maybe you can come up with something different.