I genuinely don't know if it was a bug or intentional behavior like TFA, but on the last win10 machine I used Edge would leave several of its background browser engine processes running indefinitely after the application was closed. Seems like they're just happy to let their users make unwitting sacrifices for their convenience of their devs.
Now I never understood why the chrome.exe's would hang out when I didn't install any "background apps" - anyway I suspect a similar setting in Edge is buried in there somewhere.
I have a vague recollection of that being related to embedded browsers in apps, and I think it was related to performance not child processes for unknown client apps.
