I do :).

transaction.abort() somewhere during the life-time of a request is potentially harmful because it implicitly creates a new transaction. That way, other code that's executed *after* transaction.abort() but *before* the ZPublisher does a transaction.commit() will therefore be committed. But you'd really want to forget the whole request.

I suggest using transaction.doom() instead. Note that this may likely require changes to the ZPublisher because it will have to check for doomed transactions and then either abort or commit.