When you fire multiple similar events at once (in the same transaction), you can now use the plural fire*Events methods to store them all in one go into the database, instead of one-by-one. This increases throughput.
If you used EventLogRepository.persist directly (you shouldn't!), it was previously storing the database ID of the new object back into the EventLog object. This is not happening anymore (in exchange for more efficiency for bulk inserts).
140 Persist multiple events in batch
Sketch for the Release notes:
fire*Events
methods to store them all in one go into the database, instead of one-by-one. This increases throughput.