The drivers transactions specification requires that any write concern configured at the collection level is ignored when in a transaction. For the most part, the driver does this, but in the case where that configured write concern is unacknowledged, that write concern is incorrectly applied to make several wrong decisions, including:

• Configuring the OP_MSG to not generate a response
• Not returning the result of the write