That’s correct and expected, yes. As host migration is not supported at the EOS Session level, when the session owner leaves, the session will eventually be destroyed on the backend.
After 3 minutes of no SDK heartbeat from the owner, the session will stop being returned from searches, and after 15 minutes the backend will assume the session is dead and drop the data.
If the SDK does tick again after that period, it will actually silently recreate the session on the backend without the need for additional logic.