Memory leak when using JetstreamContext.publish() #793
Description
Observed behavior
JetstreamContext's .publish() creates a very visible and easily reproducible memory leak.
We accidentally used it instead of the Client.
Switched over to Client's .publish, suddenly the memory leak is gone and publishing a message is a lot faster.
Expected behavior
Client's .publish() and JetstreamContext's .publish() to behave the same way.
Server and client version
2.12.0
Host environment
No response
Steps to reproduce
No response