Laravel multitenancy on Octane without leaking PDOs

If you're running multitenancy on Laravel Octane using the pattern most quick-start guides show, you have a bug. Either you're leaking the previous tenant's PDO into the next request (a security incident waiting for a paging shift), or you're burning a fresh TCP + TLS + auth handshake on every request (latency you'll feel the moment your tenant database lives in another region). This isn't a theoretical problem. It's the first thing that breaks when you move a hand-rolled Laravel multitenant ap...