Not all sockets closed immediately when Purge() is called.
Created by: peter
When a job is Purged, sockets that are within a scheduler are not immediately closed. They are closed only when there is action on that socket as that is what triggers epoll to return the socket. The issue is that there is a dynamically allocated callback function associated with that socket via an epoll event.