I'm also having this problem on SQL 2008 R2. You could write an ugly parsing procedure to extract the schedule_id from the message field in the stepid=0 record of sysjobhistory after the job has ran. That's the closest I've been able to come up with.