Might be worth looking to see if the processes are creating hidden windows or other UI objects. The previous post references NtGdiCloseProcess, and it'd make sense that some of those handles would require a lock to clean up safely.
The test code is up there. The master process loads user32.dll and makes a couple of window-type calls, but the other processes do nothing but wait on semaphores and then die.
