TCP connections with the status FIN_WAIT_2 are those, which are not closed correctly with shutdown(). This maybe caused by JobScheduler, but normally it sends the shutdown() command to close the connection finally.
Propably it is a problem of the browser, but after 120sec in FIN_WAIT_2 state the connection will be closed anyway.
There is no way for JobScheduler to manipulate this behaviour.
If a connection for JobSchedulers port itself is in FIN_WAIT_2 state you can use the -reuse-port option.
see also: What is a FIN_WAIT state?