Each service is creating 2 seperate node processes

I don't really know if this is a bug, or something that is expected behavior. But it seems odd to me.

I have 2 seperate windows services for our Production Node server doing two seperate things. When I start them up, I noticed there are actually 2 processes that start for each service. One on the port I am telling it, and one a seemingly random high port. I even started a third service for our test environment, and noticed 2 more processes start up. I have this Powershell command that spits out all processes and details about them with a given name.
`Get-NetTCPConnection | Where-Object { $_.State -eq "LISTEN" } | select @{Name="Process";Expression={(Get-Process -Id $_.OwningProcess).ProcessName}},owningprocess, localaddress, localport, creationtime | where Process -eq "node" | Format-Table -AutoSize`

So when I run that with my two services started, I get this:

I should add that we did have "auto-recovery" turned on for those Node services earlier today when I was having these issues. But I have since disabled that on all of our Node windows services.