NaN in a sent message becomes null when received

Hi folks,

It seems that when a worker sends to a master a message containing fields with NaN values, the master receives those fields with null values. Is anyone aware of this issue? Can this be fixed without writing a bypass (e.g., to avoid NaN)?

Regards,
-- Erez Hadad