Hi Andrei,
Thespian will normally clean up actors when the ActorSystem exits, but one common misunderstanding is that the multiproc-style Actor System Bases will startup as daemon (standalone) processes and must be actively shutdown by the application when it exits (via the `ActorSystem.shutdown()` call) if the application does not wish the Actor System to persist. Commonly multiple applications can exist (and even inter-operate) using a single Actor System framework.
It's also possible based on your other message that you have written actors that do not return from their `receiveMessage()` method; an Actor must return from that method in order to receive subsequent messages, including the `ActorExitRequest` message. Thespian will try to use signals to stop non-responsive actors when the Actor System is shutdown, but sometimes those actors are doing things that don't respond to signals either.
-Kevin