Powershell Script started with SshCommand keeps running even after connectivity loss

I wanted to start a specific .ps1 file with SSH, so I tried running the script with both SSH.NET and SSH on the Terminal. After testing a little bit I noticed, that after a connectivity loss the Script started with the Terminal drops itself regardless of the progress, on the other Hand with SSH.NET the .ps1 file keeps running even if the connection is dropped.

for SSH.NET I used this Code to start the .ps1-File:

sshc.Connect();
using (var cmd = sshc.CreateCommand("powershell.exe -command C:\\Test.ps1\""))
{
    cmd.Execute();   
}
sshc.Disconnect();

So I want to know why does SSH.NET keeps the script alive and is this a wanted feature

Start with the shown SSH.NET flow using Connect(), CreateCommand(), Execute(), and Disconnect(), then reproduce the behavior by dropping connectivity during C:\Test.ps1. Compare it with the terminal's behavior and determine whether command execution is expected to continue after the SSH connection is lost; document or test the resulting behavior.