The app.AppImage is staged to the network share and started on the remote host. The AppImage might eat all the RAM and the AppImage will get OOMkilled but sshd is unlikely to be killed. When the AppImage gets OOMkilled, the ssh session will end with an error and the ssh client will report that the session terminated unexpectedly.
I've done it (and later cringed). But it definitely works.
(But I guess it wasn't the fault of that deployment -- you just staged the binary, you didn't start it running.)