No, this is something the program does itself, not WinCE.
The program will make a call to FindWindow
(
) with its window class or name right at the start before it registers a window class and opens it. If FindWindow returns a window, it'll call SetActiveWindow to activate the already running copy, then terminate.
You could, theoretically, reverse engineer the program to block out the call to FindWindow, but that's a lot of hassle for something that probably won't work anyhow because of the TCP/IP stack