fix client connection registration with wrong address

ClientConnection should be registered with its own remote address.

In aws env, client was registered with its public address but trying to be removed with private address. Since connection can not be removed, client was ending up with a useless connection to its members. And after that client is not able to recover related connection. 

fixes  #4190