v1.9.2

• Another attempt to cleanup close Exceptions from the log. I've removed CA resource cleanup code from session write thread, and various other locations - we now simply rely on the contract with the WebSocket API onClose() method to cleanup CA resources. Avoiding concurrent calls to CAJContext.destroyChannel() looks like a good way to avoid close Exceptions. Other threads still check if the session isOpen(), but no longer try to clean up resources since that is already being handled onClose().