I've observed the same issue - and appreciate having this post to help me along.

Um - however I don't think using the system stored procedure msdb.dbo.sp_purge_jobhistory  will work...