A potential memory leak was identified in 5.x version.
The leak behavior appears to be rising slowly, but steady.
Taking a heap dump, would reveal the issue, inspect the map in
More investigation showed that the problem is related to recent change in event based push replication behavior, specifically when a failed initialization of a replication has occured, a connection is being added to the map, but never being closed.
Failed replication initialization will continue to try initialization every 1 minute. A simple error with the remote repo will contribute to the leak, for example: bad url or bad credentials configured on the remote repository.