scan.exe consuming high file handles and locking up Windows nodes

We have had this happen twice now on "high criticality machines" where the scan.exe consumes a high number of file handles and causes the Windows end node to not allow any more applications to be launched by the admins.
Is there a way to limit the number of concurrent file handles used by scan.exe