This is a regression issue after updating from v0.4.x to v0.6.x of Node.
Originally, if trying to immediately connect to a port returned from the status check, the socket connection may not have finished closing. Now returns the status after the connection has finished closing on the socket.
The original names of `findAnOpenPort` and `findAClosedPort` were ambiguous. While the functions were referring to port status, open could be interpreted as available. New functions are `findAPortInUse` and `findAPortNotInUse`. Verbose, yes. I am open to suggestions that keep the same tense and verb usage. So, not `findAnAvailablePort` and `findAPortInUse`, for example.