Avoid unneeded TimerImpl instances during db refresh

For ejb timers with database persistence, during a db refresh, many TimerImpl instances are created from query ResultSet, and many of them are not actively used. They are subsequently thrown away and gc'ed, which increases the gc burden.

We should only create TimeImpl instances from ResultSet when really needed.