SP2 Time based publishing: TBP EventListener is very long and time consuming on large TMB changes

I put a time based publishineg end dat on the home page of my 10'000 pages test site yesterday (cf parent bug). Today the content expired. I restarted the server and, for the last hour, I have some TBP processing + Lucene reindexing running and taking 100% of my CPU.

What is also strange is that, at startup, and when clicking on pages with guest user in live mode, I can perfectly access to expired content until their status is changed. There is no check when accessing to the page. So if the event listener has not run (and here again this is a process which can takes hours), a user can perfectly access to the obsolete content.

Yourkit snapshot in attachment (30 seconds extract of the load)