We have 100% seen issues with both Client load balancing and band steering (Band load balancing) algorithms in the past.
What I have found is that when a AP is overwhelmed, the AP encourages devices to switch by increasing latency to specific devices. One the other end, if an AP has identified itself to have too many clients, it may intentionally not respond to new connections in an attempt to encourage the device to look elsewhere.
In either situation, this promotes a environment that pushes clients to roam to other accesspoints that may not accept the roam request. Which could cause a problem.
If the area is congested and AP's are shedding clients, this could very well be the situation. But without knowing why the client attempted to roam, and if the request to join the new ap was successful, it's all a shot in the dark.
It could entirely be a chromebook firmware issue. It could entirely be a Wireless network design issue. Could also be a student induced problem (though not sure how). More investigation is really needed.
The fact that the device requires a reboot to reconnect makes me concerned this is more of a device issue.
Even if it is a device issue, the packet capture and/or log of the AP's would help in identifying and reporting the issue to Google.