Even if you set a port's edge-status to yes, there is still spanning-tree protection, but you may get a small amount of flooding until spanning-tree detects the loop and blocks it.
The other reason you need to set the edge-port status is so that when a port comes online it does not trigger a topology change. In a large enough network with ports going online/offlne fairly regularly this can be a real problem.
RSTP on ProCurve switches defaults the edge-port status to yes.
MSTP is going through a bit of a transition at the moment, previously it defaulted edge-port no - but new firmware releases now will use auto-edge-port as default.
The other feature I would consider enabling is the loop-protect feature, as some phones do not forward spanning-tree BPDU's - so a loop could be created and not detected. Some switches also 'eat' BPDU's - the 1800 currently does but I believe this will be changed in a future firmware release.
For your AP's, since they are part of the infrastructure it's not so important to set the edge-port status since they will always be up.