This is something stupid I did, but I want to report it anyway because maybe it is just the symptom of a bigger issue.
This happens on Magnolia 4.4 and 4.4.1, with or without workflow module. Steps to reproduce:

• change the active subscriber to the same instance in use (making Magnolia pointing to itself)
• delete a page (you'll see the new icon and such)
• publish the change
  The publication fails (as expected), but the deleted page is gone.

Making an instance point to itself is just stupid and pointless, I know, and it's not something you should usually do. Until the previous version any activation would just do almost nothing (or fail sometimes), and any de-activation would simply fail (it's quite obvious). With the new version I would expect a similar behaviour, but the deleted page is gone even if the activation failed.
By the way, I may expect that self-publishing a deleted page would really delete the page, I do not expect that the page is gone after a failure... The question may be: what to do with an authoring error happened after the page was succesfully deleted on the public machine? If the activation should be considered transactional, should the page be restored on the public machine in case of an authoring error after deletion?