Destroy AsyncHttpEncryptionAwareConduitFactory object when WinRMService instance is closing #73

When WinRMService is closed, the AsyncHTTPConduitFactory.CloseIdleConnectionThread continues running, resulting in a thread leak.

This issue occurs because WinRMInvocationHandler creates a new instance of AsyncHttpEncryptionAwareConduitFactory but does not invoke its shutdown() method. As a result, the internal thread responsible for managing idle connections is not terminated properly.

Suggested Fix: Ensure that any instances of AsyncHttpEncryptionAwareConduitFactory are explicitly destroyed when closing the associated org.apache.cxf.endpoint.Client objects. This will guarantee that all background threads are properly shut down and prevent resource leakage.