SEP Firewall prevents immediate dropping of orphaned SQL processes

Win7 64 + SEP 12.1 to SQL 2000 on Win2k3

Prior to installing SEP 12.1, SQL processes orphaned by client application termination were dropped immediately.

Typically this happens when Task Manager is used to "End Task" an unresponsive application due to a deadlock.

Subsequently it now takes a few minutes for orphaned SPID’s to automatically drop along with the locks they hold.

Disabling the SEP firewall restores our environment to the desired behavior where the orphaned processes are immediately dropped.

Question: What firewall rule at the SEPM group policy must be set to restore the desired behavior above?

Thank you!