Kstream app with state store using deployment vs statefulset

we have kstream app running in production EKS cluster , it uses state store for look up from topics (enrichment) . We are trying to persist the state store using persistent volume claim.Most of the confluent forums/blogs from internet recommends to use statefulset with pvc. i would like to know what is the disadvantage of using deployment with multiple replicas of the app with same consumer group read using volumeclaim from the same PVC ,instead of statefulset. as we know statefulset attaches one volume for each replica and maintains the stickness after pod restarts.