okay...did some aggressive testing and work arounds on this. figured out a few things...
i was using the windows appbuilder and emulator to test. it caches locally (in browser? on local drive?) tokens gathered by the getaccesstoken function. kept using that and i couldn't get rid of it. when i tested the facebook-api sample using telerik platform, it works. it also works with test accounts that have been assigned to the facebook app.
i decided we will not use telerik's user-account facebook login steps but instead the jso.js functions for facebook provided by their facebook-api sample. since we have our own login requirements and user/pass stored on internal servers (not telerik), i think this will reduce any user account issues that may come up -- or at least any problems with user accounts will be in one place.
