That’s what I suspected. So I tested and found that I get the same thing even if both eth1’s are connected to the LAN. My senior colleague suggested that it’s a flaw in WireShark. Perhaps I should ask on one of their forums.
But that is a side issue. I read the ARP RFP, and it provided no insight into the original question.