Might be custom implementation or configuration causing this & will not happen oob. Not heard such thing so far with any hotfix atleast. Possible suspect to look are
chain replication configuration
workflow lauuchers
custom listeners.
Offcourse log should give you enough information.