if you have two stand-alone access points, AP1 does not know anything about the sessions active on AP2
just because they use the same SSID name, they still are separate WLAN's
when the client is connected to SSID1 on AP1 and comes in reach of AP2, the client thinks it is connected, but the AP2 thinks not!
that's where wireless controllers are designed for, they provide an central administration of sessions over multiple access points.
alternative is Cisco Mobility express where one AP functions as controller, At this time i'm not sure the WAP561 supports this.
some modern (home) AP's use technique to communicate with one another called "mesh".
apart from above there can be some bug or incompatibility with the smartphones used. but we we need more information about software version on the WAP, configuration and clients