I saw a similar issue and raised a topic here about a month ago.
I was advised that the "Force DHCP Option" should only be used when roaming across subnets- although that wasn't the way I read the documentation either.
I was using 10.0.0.0.1424 GA (the latest release) and saw similar problems as devices (particularly Apple) moved from AP to AP.
Things were pretty stable and worked "as expected" until a roaming event occurred.
I've left it turned off, but would prefer to have it enabled. To me it makes sense to prevent statically addressed clients connecting.
Hope that helps a bit.