Persistent scheduler is not deleting completed jobs, the reason we keep the completed jobs is we want to show client(or administrator) the status of the persistent jobs(completed, paused or running).

The problem here is there may be lots of completed jobs in database(for example, Sesame project schedules dozens of pages for publication every week and many of their pages get published at least once per week), and it will load into memory every time restart server, it may cause bad performance both on the view page database.

The solution is to use Audit Portlet. Delete the persistent jobs once finished, meanwhile send a audit message to record the actions.
We will not use Audit Portlet to show the history of job actions, cause it is different from other kind of resource that use Audit Portlet, will provide this function in Scheduler Management Portlet in the future.