EJB3 CalendarBasedTimeout computes incorrects timeouts due to bad Calendar time fields manipulation, specially on DST.

A couple of examples:

1) Timezone: "Europe/Lisbon"
Schedule Expression: any day at 1h30m
Start: 2013/03/31 03h30m
First timeout currently is 2h30m

2) Timezone: "Australia/Lord_Howe"
Schedule Expression: any day at 2h20m, 2h40m, 3h20m, 3h40m
Start: 2013/10/06 02h41m
First timeout currently is 3h50m