From a user report in our Telegram channel:

I'm using bitbox.Socket to listen for address activity and noticed that each call to socket.listen creates an additional TCP connection for its query and callback but socket.close only closes the first one that was created.

The scope of this issue is to investigate this claim. The deliverable is code that reproduce this issue of creating multiple TCP connections.

I've seen behavior on the back end that suggest that some apps are creating redundant connection which slows down both the server and end-user app.