It is a limitation of the mocl runtime. mocl uses a single stack that is shared across threads. Therefore simultaneous Lisp threads of *any* kind may interfere with each other by overwriting the stack of the other.