Yups - that was a bug alright.
Apparently I never considered that the script called on quest-start could fail the quest right away. As a result, the server kept working with the data as if the quest was still valid, and crashed. ;P
It's fixed now. Thanks!