Depending on what network gear you're using (I'm now switching to Omada, previously/still on some site son UniFi, but lots of even 'prosumer' stuff does this) there are specific mitigations available. All of this falls under the heading of "managing broadcast traffic", which is very important even for smaller networks. The three major categories of traffic on a network are unicast, broadcast, and multicast. Unicast is the normal case of one device talking to a single address. Broadcast involves sending a packet to every single possible recipient in the entire broadcast domain (almost always the subnet). ARP fits in here. Multicast is essentially in between, more efficient then broadcast, can still talk to multiple devices that have signed up to hear it.

Obviously an actual broadcast storm can take down an entire network, but excessive broadcast traffic on WiFi specifically can also suck up a huge amount of airtime for little bandwidth. Every single device has to go to the slowest speed and stop what they're doing to listen and make sure no one is left out. Using STP/RSTP with proper values set and LACP for aggregated interfaces can help prevent inadvertent network loops. Many switches also support some kind of port isolation and explicit per port storm control restricting max numbers of packets/second for unicast/broadcast/multicast traffic. WiFi APs can use proxy ARP to cut it in their domain too. The WAP already of course knows the MACs of every device connected to it by definition, so there isn't generally any reason not to have it answer ARP requests on their behalf then forward the traffic itself.