In my previous post, Beware of Cascading Deletes in WSS/MOSS, I noted that this was confirmed to be a bug, but after review and a few discussions with key folks in Microsoft, it turns out that this is actually a by design behavior for this release. The SPM that I emailed when I discovered this, got the this issue mixed up with some other bugs that were being fixed and confirmed incorrectly originally.
Please note, that the SharePoint Product Management team is is definitely interested in any customer feedback to consider for improvements.
I’ve been heads down quite a bit in development, but thought that I would take a moment to state that this is actually “By Design”. 😦