That is by design. At the time that the "on socklisten" event triggers, the connection has already been fully accepted by the WinSock stack, and thus the other side already perceives it as being open at that point - regardless of what mIRC does. If the script still causes the connection to not be "accepted" after all, all mIRC can do is close it again.
