if saved object contains LocalDate(Time) fields, and is read on the server with different timezone than on server that did the save, such field will have different values on two servers.
This is OK for java.util.Date, or DateTime, because in terms of Epoch values are equal, but in case of LocalDate(Time) there's no way to compensate TZ (this information is lost), or even detect such situation.
I didn't have a chance to check it with java.time.* classes, but I suspect it is broken in similar way.
My (temporary?) solution was to write custom converters which adds/subtracts current TZ offset to compensate java.util.Date TZ.